Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to CREATE TEMP TABLE in SQL generation when necessary. Previously we assume RAND() in the WITH clause behave as if they are evaluated only once, but that's not always the case. In situation when that's not true, we need to CREATE TEMP TABLE to materialize the subqueries that have volatile functions, so that the same result is used in all places. #224

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Dec 28, 2024

Allow to CREATE TEMP TABLE in SQL generation when necessary. Previously we assume RAND() in the WITH clause behave as if they are evaluated only once, but that's not always the case. In situation when that's not true, we need to CREATE TEMP TABLE to materialize the subqueries that have volatile functions, so that the same result is used in all places.

@copybara-service copybara-service bot force-pushed the test_710112682 branch 9 times, most recently from 25138d4 to 9691afd Compare January 3, 2025 22:30
@copybara-service copybara-service bot changed the title Allow to use the Datasource as a TEMP TABLE. Allow to CREATE TEMP TABLE in SQL generation when necessary. Previously we assume RAND() in the WITH clause behave as if they are evaluated only once, but that's not always the case. In situation when that's not true, we need to CREATE TEMP TABLE to materialize the subqueries that have volatile functions, so that the same result is used in all places. Jan 3, 2025
…ly we assume RAND() in the WITH clause behave as if they are evaluated only once, but that's not always the case. In situation when that's not true, we need to CREATE TEMP TABLE to materialize the subqueries that have volatile functions, so that the same result is used in all places.

PiperOrigin-RevId: 710112682
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant